Data parking within offline community system

ABSTRACT

A data parking in an offline community system comprising a discovery module configured to identify at least one device that has gone offline due to an event, a community, the community including at least one data source, the data source including the identity of the at least one device; and a mobile aggregation device movable between a first position where the mobile aggregation device is in communication with a network to a second position to establish communication with the at least one device; wherein the mobile aggregation device is configured to aggregate data from the at least one device and store it until returning to the first position.

TECHNICAL FIELD

The disclosure relates to networked resources, and more particularly toa data parking within an offline community. Most particularly, thedisclosure relates to a data parking system that includes a mitigatingoperational protocol using a mobile aggregation device to transportaggregated data to one or more devices in an offline community.

BACKGROUND

As devices become more ubiquitous and natural disasters or otheremergency conditions affect more individuals, the need for fast,decisive, and regimented recovery operations becomes increasinglyimperative. One shortcoming of existing infrastructure is the need toemulate or recover a normal operational mode before most network devicescan resume any operation. Additionally, when communicating betweennetwork assets that may go on-line and off-line, such as duringintermittent power or connectivity, these network components must learnhow to efficiently aggregate and distribute data and messages.

This disclosure is directed to solving one or more of the problems inthe existing technology.

SUMMARY

According to an example, the disclosure generally includes a dataparking in an offline community system comprising a discovery moduleconfigured to identify at least one device that has gone offline due toan event, a community, the community including at least one data source,the data source including the identity of the at least on device, and amobile aggregation device movable between a first position where themobile aggregation device is in communication with a network to a secondposition to establish communication with the at least one device,wherein the mobile aggregation device is configured to aggregate datafrom the at least one device and store it until returning to the firstposition.

Another example includes a network device comprising: a processor, aninput/output device coupled to the processor, and a memory coupled withthe processor, the memory comprising executable instructions that whenexecuted by the processor cause the processor to effectuate operationscomprising discovering an event where at least one device is offline,instantiating an emergency mode causing the at least one device topermit data or message aggregation; instantiating a community includingthe identity of the at least one device, establishing a communicationbetween the at least one device and a mobile aggregation device, andwhen the mobile aggregation device is in communication with the at leastone device.

BRIEF DESCRIPTION OF THE DRAWINGS

In the following description, for purposes of explanation, numerousspecific details are set forth in order to provide an understanding ofthe variations in implementing the disclosed technology. However, theinstant disclosure may take many different forms and should not beconstrued as limited to the examples set forth herein. Where practical,like numbers refer to like elements throughout.

FIG. 1A is a representation of an exemplary network.

FIG. 1B is a representation of an exemplary hardware platform.

FIG. 2 is a representation of a data parking system according to anexample.

FIG. 2A is a representation of the system according to another example.

FIG. 2B is a representation depicting operation of the system accordingto an example.

FIG. 2C is a schematic representation of a display generated by thesystem in response to an event.

FIGS. 2D and 2E are a flow diagram depicting operation of a systemaccording to an example.

FIG. 3 is a representation of a network device according to an example.

FIG. 4 depicts an exemplary communication system that provide wirelesstelecommunication services over wireless communication networks that maybe at least partially implemented as an SDN.

FIG. 5 depicts an exemplary diagrammatic representation of a machine inthe form of a computer system.

FIG. 6 is a representation of a telecommunications network.

FIG. 7 is a representation of a core network.

FIG. 8 is a representation packet-based mobile cellular networkenvironment.

FIG. 9 is a representation of a GPRS network.

FIG. 10 is a representation a PLMN architecture.

DETAILED DESCRIPTION

A data parking system is generally indicated by the number 200 in theaccompanying drawings. As described in more detail below, system 200includes a mitigating operation protocol using one or more mobileaggregation devices to aggregate and deliver messages and data within aparked, i.e. off-line, community on a network.

The network may include a telecommunications network, software definednetwork, local area network, and the like. Examples of various networksare provided in connection with FIGS. 4-10 and described below. The edgeorchestration system 200 in the following description may be implementedwithin one or more of the various networks. Moreover, as discussed morecompletely below, system 200 may be instantiated as a network devicewithin such networks or a virtual network function on a network.

FIG. 1A is a representation of an exemplary network 100. Network 100 maycomprise a software defined network or SDN that is, network 100 mayinclude, one or more virtualized functions implemented on generalpurpose hardware, such as in lieu of having dedicated hardware for everynetwork function. General purpose hardware of network 100 may beconfigured to run virtual network elements to support communicationservices, such as mobility services, including consumer services andenterprise services. These services may be provided or measured insessions.

A virtual network function(s) (VNF) 102 may be able to support a limitednumber of sessions. Each VNF 102 may have a VNF type that indicates itsfunctionality or role. For example, FIG. 1A illustrates a gateway VNF102 a and a community function (COMM) VNF 102 b to facilitate datasharing within a community as described below. Additionally oralternatively, VNFs 102 may include other types of VNFs including butnot limited to security, routing, wide area network (WAN) optimizationand others within a service providers virtual network offerings.

Each VNF 102 may use one or more virtual machine (VM) 104 to operate.Each VM 104 may have a VM type that indicates its functionality or role.For example, FIG. 1A illustrates a discovery module (DM) VM 104 a and acommunity module (CM) VM 104 b. Additionally or, alternatively, VM 104may include other types of VMs. Each VM 104 may consume various networkresources from a hardware platform 106, such as a resource 108, avirtual central processing unit (vCPU) 108 a, memory 108 b, or a networkinterface card (MC) 108 c. Additionally or alternatively, hardwareplatform 106 may include other types of resources 108.

While FIG. 1A illustrates resources 108 as collectively contained inhardware platform 106, the configuration of hardware platform 106 mayisolate, for example, certain memory 108 c from other memory 108 a. FIG.1B provides an exemplary implementation of hardware platform 106.

Hardware platform 106 may comprise one or more chasses 110. Chassis 110may refer to the physical housing or platform for multiple servers orother network equipment. In an aspect, chassis 110 may also refer to theunderlying network equipment. Chassis 110 may include one or moreservers 112. Server 112 may comprise general purpose computer hardwareor a computer. In an aspect, chassis 110 may comprise a metal rack, andservers 112 of chassis 110 may comprise blade servers that arephysically mounted in or on chassis 110.

Each server 112 may include one or more network resources 108, asillustrated. Servers 112 may be communicatively coupled together in anycombination or arrangement. For example, all servers 112 within a givenchassis 110 may be communicatively coupled. As another example, servers112 in different chasses 110 may be communicatively coupled.Additionally or alternatively, chasses 110 may be communicativelycoupled together in any combination or arrangement.

The characteristics of each chassis 110 and each server 112 may differ.For example, FIG. 1B illustrates that the number of servers 112 withintwo chasses 110 may vary. Additionally or alternatively, the type ornumber of resources 110 within each server 112 may vary. In an aspect,chassis 110 may be used to group servers 112 with the same resourcecharacteristics. In another aspect, servers 112 within the same chassis110 may have different resource characteristics.

FIG. 2 shows a representation of a system 200 according to an example ofthe disclosure. In the example, system 200 includes a mobile aggregationdevice 210 that facilitates communication with a parked community i.e.one or more devices 220 that are offline. The parked community may beoffline for any reason including but not limited to a natural disaster,power outage, coverage outage, network failure, or other failure. Forpurposes of example, we will collectively refer to the lack of access oroutage as an emergency. The result of the emergency is that affecteddevices are off-line i.e. parked. Using wireless mobility as an example,the emergency disrupts service. Devices 220 in that area receive noservice. In turn, the devices may display a no service signal to a user.Under these circumstances, an attempt to communicate in the emergencyzone would cause the outgoing signal to fail. For example, if an attemptwas made to send a text, the text will not be delivered, and the deviceattempting to send the text would display a “not delivered” or similarmessage.

According to the example, system 200 provides a mitigating operationprotocol (MOP) that allows the network infrastructure in an event areaor zone Z to operate in a quasi-stable hybrid state. In this state, datais delivered in batches while leveraging existing assets with nobackhaul resources. Once an emergency is detected, data is parked untilit can be retrieved as discussed below. Devices 220 within the emergencyzone Z may be identified and, if possible, set to an emergency mode.System 200 may also generate a community 230 of devices based on thedevices identified as being within the emergency zone Z, parked devices.

According to one example, MOP may include a virtual network function,network device or other dedicated apparatus connected to a network 100that upon detecting an emergency, performs operations includingpreemptively setting devices 220 (1 . . . N) identified as beingaffected by the emergency in an emergency mode. This operation mayinclude automatically placing the device 220 in an emergency modewithout feedback. System 200 may also await feedback, or a lack thereof,before placing the device in emergency mode. For example, system 200 maysend a signal to a device 220 inquiring as to the status of the device220. If no response is received indicating that the device has lostconnectivity, a signal may be sent to place the device in emergencymode. For example, a signal may be sent to a tower that in turn maybroadcast the emergency mode signal to devices that are offline. Ininstances, where the tower or other network broadcasting element iswithin an event zone and is unable to communicate with the core, thetower may place itself in emergency mode. To that end, tower or otherdevice may check for the existence of conditions such as a loss ofcommunication with a core network or loss of backhaul communication, andwhen such conditions exist, switch its operation to an emergency mode.When switched to emergency mode, tower or other device may broadcast asignal to switch devices within its communication range to emergencymode as well. Such a condition may include a time element, for example,if communication with the core network or backhaul communication is lostfor a period of at least 6 hours, the tower switches to emergency mode.As an alternative or in addition to this feature, the tower may bemanually switched into emergency mode via a signal from an MAD. In thisway, if an event is detected, an MAD may be deployed to switch the towerbefore the time limit is reached providing greater responsiveness thanthe tower's internal conditions. Likewise, when the conditions thatcaused the tower or other device to enter emergency mode no longerexist, the tower or device may automatically switch back to normaloperating mode. Automatic operation may check for the existence ofconnectivity with the core network or backhaul communication to triggera switch back to normal mode. Again to avoid cyclical switching whenthere is intermittent connectivity, the device may require connectivityfor a time period before reverting to normal mode. Also, the tower ordevice may be switched back manually through a signal from the corenetwork when connectivity is established or in some instance via asignal from MAD.

According to another example, system 200 predicts the flow/target forthe area affected by the emergency by observing and adapting to networkconditions.

System 200 may instantiate a community 230 that includes these parkeddevices. To that end, system 200 may employ discovery module VNF 104 ato identify and inventory the devices that are off-line. A communitymodule VNF 104 b may gather data related to the devices to better definethe community 220. As schematically shown, MAD 210 may communicate withcommunity 230 via a traditional network 100 including the examplenetworks described in more detail with reference to FIGS. 4-10.Community 230 may, at least in part, be instantiated within MAD andmemory stores 226 for device ID and location information and commands orsignals including civic authority data 228 may also be instantiatedwithin MAD 210. As the MAD 210 moves between a first location where itcommunicates with network 100 and a second location where itcommunicates with the parked devices 220, data may be staged in astaging memory store 229 before being transmitted to MAD 210. Likewise,upon establishing communication with network 100, MAD 210 may provideupdates to a civic planning authority data store 241 including but notlimited to device ID and location data and civic authority data.

With reference to FIG. 2A, community 230 is a managed asset and may beinstantiated as a network device or virtual network function. Community230 includes a cohesive set of functionality including software definednetworking, orchestration and analytics to enable data sharing andcollaboration. Community virtual network functions enable dynamic,on-demand combinations of data sourced from one or more entity andmerged into a community 230 to derive insights in a highly secureenvironment. The community 230 may be closed in the sense that accesscontrols or security functions are in place to execute user privacysettings, network policies, government regulations or other limitationson access to the data and related functionalities within community 230.Identity and access management 233 may orchestrate and monitor access tothe community 230. For purpose of analytics, community 230 may include amachine learning tool 232 and an artificial or augmented intelligencetool 234. These tools may be instantiated as a network device or virtualnetwork function within a SDN.

A community is defined and stored within a data platform in a network100, such as for example, an Indigo® platform or the like. In oneexample, community 230 includes an audit ledger 250, such as ablockchain ledger. Community 230 may be a data community, a rolecommunity, a privilege community and combinations thereof. In theexamples discussed herein, a data community may simply gather data fromthe emergency zone including but not limited to device data includingbut not limited to whether a device has service, what mode a device isin, whether the device is transmitting, the location of the device, anyinput data received from the device, or other data generated by thedevice. The data community may further include network registrationinformation (device on, device activity detected, etc.), query dataobtained from device surveys, or other message information. A rolecommunity may leverage device related data to define roles ofusers/devices. A privilege community may assign functionality andnetwork privileges based on a role or data. For example, a privilegecommunity may provide additional data delivery, enhanced devicefunctionality or network service, or push data to a particular devicebased on the devices role as a first responder device. Additionalcommunities may be defined to further link data and network services.For example, an emergency community may include any device presumed tobe affected by the emergency based on location or other information.Additional sub-communities within the emergency community may includeoutage devices, confirmed devices, normal activity devices, andprioritized devices, or other categories of devices relevant to aparticular emergency. As described more completely below, interactionsof the system 200 with devices 220, including but not limited to surveysor queries, may be used to infer the state of a device 220 and updatethe devices status or storage within a community 230.

According to a further example, additional device communities may begenerated to provide selected devices with special roles, priority andprivileges. For example, FirstNet access may be provided to certaindevices identified as being within a first responder community,technical service community or other community that may need differentaccess or privileges to data and connectivity in view of the emergency.

Examples of the MOP including instantiating of one or more communitiesin connection with an event, such as an emergency will be discussed withreference to a simplified example shown in FIGS. 2B and 2C. FIG. 2Bschematically depicts an event E, such as an emergency occurring near atower 216. The event E may be anything that affects or limitscommunications between devices 220 and network 100. It will beappreciated that event E may include planned and unplanned outages orlimitations on service. For purposes of example, an emergency event willbe considered, such as, a natural or unnatural disaster that damagesnetwork assets or power supplies to such assets resulting in loss orimpaired service within the area or zone surrounding the damage. Thezone may not be as clearly defined as shown in the depicted example asthe assets and devices affected may be scattered across a geographicalarea. The example, thus, should not be considered limiting.

With reference to the example in FIG. 2B, the event E has affectedservice surrounding the tower 216 forming an emergency zone Z. Devices220 within the zone Z do not have service. As shown, a device 220 may bein the emergency zone Z and within communication range of a tower 216.Using the text message example, when a user within the emergency zoneattempts to send a signal S carrying the text from device 220 to areceiving device 222, the text may be received at the tower 216, but dueto the emergency outage, it cannot be transmitted from the tower 216 toreceiving device 222. In the example, a pair of devices 220 are showntransmitting signals S1,S2 respectively. It will be understood thatthere may be any number of devices 220 in zone Z such that there may besignals S1, S2 . . . Sn.

According to the MOP, when placed in emergency mode, device 220 themessage (schematically shown as SMS1, SMS2 . . . SMSn) is parked untilit can be retrieved rather than retrying to send the message until aconnection is obtained or indicating a message failed signal as in anormal device mode. In the example, tower 216 may act as an aggregationsite 215 for multiple devices 220 (1, 2 . . . n).

When MAD 210 communicates with aggregation site 215, parked messagesfrom the devices may be gathered via aggregation site 215 and uploadedas a payload 225 for delivery to a receiving site. With reference toFIG. 2B, tower 216 may broadcast a park signal P from MAD 210 to devices220 indicating that the message was received and is parked. When anaggregation site is not used, as depicted in FIG. 2, park signal may betransmitted directly from MAD 210 to device 220. The park signal P maycontain additional information as described below. The mobileaggregation device 210 retrieves the parked data and facilitates itscomplete transmission. Mobile aggregation device 210 may be acommunication device capable of being moved into the emergency zone Z orat least into communication with emergency zone Z to facilitatecommunication of the data parked according to the MOP outside of thezone Z. Example MADs include but are not limited to a communicationsvehicle, such as a drone, UAV, a dirigible, a cell on wheels (CoW),parachute, temporary satellite access module, balloon, or similardevice.

The MAD 210 is brought into communication with a device directly or ifavailable with an the aggregation site, generally indicated by thenumber 215. In the example shown in FIG. 2B, aggregation site 215 is atower 216. It will be understood that an aggregation site 215 mightinclude other network equipment including other mesh or fixed assetswith no back haul resources. MAD 210 gathers the parked messages vitower 216. Once MAD 210 has gathered the parked messages and stored themwithin its memory as payload 225, it is moved to communicate themessages downstream to the intended recipient. This may involve havingMAD 210 moving into communication with a receiving site, such as asecond tower 217 that is in communication with the network such that theparked message is transmitted via the network to the recipient device222. In other examples, where both sender and recipient are within zoneor where multiple zones exist at the same time, MAD 210 may travel toanother aggregation site or other point where communication may beestablished to transmit the parked message. It will be understood thatin some instances, moving MAD 210 into the zone Z to establishcommunication with the aggregation site 215 may be sufficient totransmit the parked messages downstream. For example, MAD has sufficientsignal strength to transmit to an unaffected tower 217. In otherinstances, as schematically shown in FIG. 2B, MAD 210 may be movedoutside zone Z after gathering the messages to deliver them to atransmission site, such as tower 217. In still other examples, multipleMADs may be deployed or used in conjunction with mesh devices to form abucket brigade to transmit parked messages. It will be understood thatthe same process in reverse would be used to aggregate messages thatneed to be delivered into the zone Z.

Often in an emergency event, in addition to a loss of service orconnectivity, there are power outages that make it important to conservebattery life for devices 220 within zone Z. As indicated above, the parksignal P may also be used to transmit a notice that a message is parked.The parked signal P may include other information including a scheduledtime for the MAD arrival at tower 216. This would allow users to shutdown devices 220 until the scheduled MAD arrival for additionaltransmitting/receiving of messages. For example, park signal P mayindicate, “turn on your phone during a selected time period to send andreceive messages, and turn it off to save battery.”

According to another example, MOP may optionally include an operationthat automatically switches the GPS radio within a device “on” toidentify a device's location. If system 200 is not able to communicatethe command to devices directly, this command may be transmitted fromMAD 210 to devices 220 when MAD is in communication with the aggregationsite 215 or devices 220. In this way, park signal P from MAD 210 mayalso include a command that alters the functionality of the device 220.In addition to activating the GPS location signal, command might alsoalter the functionality of the device to boost its broadcast powertemporarily to assist in delivering the location to an aggregation site215 and/or placing the device 220 in a low power or other powerconservation mode. The device's location may be transmitted as anemergency message to aggregation site 215 for pick up by an MAD asdescribed above.

The park signal P may also be used to send and receive mass messageswithin the zone Z to determine the status of devices 220. For example,park signal P may contain a survey or query that asks users to indicatetheir status via device 220. As an example, a survey signal may providea message to hit 1 for safe but no power, 2 for injured but stable, 3for running out of food/water, or 4 for critical medical emergency. Fromthese queries, system 200 may aggregate data including the number,identity and location of responding devices 220; the responses; or acombination of data to help identify locations of greatest need. System200 would save this data in a data store 231 associated with thecommunity 230 to provide and update device status with each MAD cycle.System 200 may use AI 233 to analyze the data to generate variousoutputs to one or more display to convey information about the devicesin the emergency community or simply transmit data to assist in effortsto address the emergency. For example, as schematically shown in FIG.2C, one display, generally indicated at 240, may include a map showingrepresentations of the responding devices' locations and responsesgraphically at 242 to inform a viewer of the areas of greatest need.Other displays, such as graph 244, may indicate the number of devicesaffected. Display 240 may also identify the last known location of thedevice 220 and status of the user.

System 200 may assign priority to data/messages in terms of aggregationand delivery to address limits in the storage capacity of the MAD 210and/or the speed of transmission of higher priority data/messages. Forexample, government surveys or other queries as discussed above, toobtain information on the emergency and those affected by it, may beassigned greater priority in terms of aggregation and delivery such thatthey receive a first in and first out placement within the MAD 210.Using the response examples above, greater priority may further beassigned based on the response type. For example, critical emergencyresponses may be given greater priority. Other tagging of messagesaggregated by MAD 210 may occur including tags that prioritize and routeresponses or data obtained from devices 220 to other online communities,such as a first responder or FirstNet community and the like to dealwith medical emergencies. Coverage maps and location data from devicesmay be routed to a technician community to identify the source of anoutage or address the outage. Likewise, devices 220 within zone Z, suchas a first responder or technician, may have a priority assigned to themsuch that they also receive priority handling of data/messages tofacilitate their response to the emergency. To summarize, based on arole identified in the community or a message, system 200 may assignvarious types of priority or privilege including but not limited to acommunications priority, time order priority, connectivity priority anddata priority or privileges. The communications priority may include butis not limited to providing greater bandwidth, message capacity,delivery speed or the like. Time order priority may include but is notlimited to ensuring that higher priority messages are the first in andfirst out from the MAD. Connectivity priority may include but is notlimited to boosting a signal at a tower serving the community memberswith greater priority or facilitating connectivity through a Meshnetwork to re-establish connectivity on a core network faster than withother devices. Data priority and privileges may include but are notlimited to providing data relating to the event or other members of thecommunity to facilitate the role of the community device. For example,event information may be broadcast to a first responder or technician tohelp them respond to the event.

While the example of an emergency is provided, it will be understoodthat system 200 may employ a similar MOP in connection with otherevents. For example, events that drive high communication volume such asconcerts, financial exchanges, sporting events or the like; events inremote locations where there is a lack of service or inconsistentservice; and the like.

According to another example, system 200 may temporarily command devicesor assets to operate out of specification in response to the MOP. Forexample, system 200 may instruct an asset to operate out of a powerspecification to boost the signal within zone Z to maximize the devicesreached by the signal. MAD 210 may as part of its connection with anasset such as tower 216 in FIG. 2B, transmit a command from system 200to operate tower 216 out of specification or otherwise boost the tower'ssignal temporarily while transmitting a park signal P. Likewise, system200 may provide a command to decrease an asset's performance temporarilyto conserve power. As with the park signal P to devices alerting thedevices of the MAD schedule, the same schedule may be used to reducesignal output at the tower 216 while the MAD 210 is out of signal range.This may conserve energy within battery or other back-ups or fuelconsumed by generators operating during a power outage.

With reference to FIG. 2D, an example of operations, generally indicatedby the number 260, performed by system 200 are described in response toan event E. When an event E is detected, system 200 instantiates the MOPat step 261. According to MOP, system 200 may instantiate an emergencymode at step 262 that provides a hybrid mode of operation for theaffected device(s). Optionally at step 263, system 200 can predict theflow or target for the affected zone Z by observing or adapting to thenetwork condition(s).

System 200 may also instantiate an event community 230 as generallyindicated at step 265. This step may include discovering or identifyingdevices affected by the event at 266, which may also include classifyingdevices based on their status, i.e. outage device, inactive device ordevice not responding) at 267. It will be understood that the status ofthe device at the moment the event was detected may be used to initiallypopulate community data store, and additional information obtained afteran MAD connects with devices may be used to update the data store asdiscussed above. The community instantiation 265 may also includegathering community data from data sources available to system includingdata stores available through the network including but not limited togovernment alert data, weather services data, geography data, emergencyprofession data, employee data, and user data. These data stores may beproprietary or third party data stores, and may include communicationwith other communities for purposes of cross-checking or obtainingadditional data. As shown, information obtained during step 267 may alsobe gathered at 268. The community instantiation 265 may also includeprioritizing connectivity or data flows within the community at 269. Forexample, as shown, priority may be assigned based on identifying adevice as being within a responder community, such as for example, afirst responder or FirstNet community, a technician community, or othercommunity that may need prioritized connectivity, communication or datato respond to the event E. When a responder is detected at 269A, system200 may establish the appropriate priority for the responder at step269B.

System 200 further performs the operation of moving the MAD 210 intocommunication with the device(s) affected by the event E as generallyindicated by the number 270. To establish communication, MAD 210 mayenter the zone Z 270A or establish a connection with device(s) that arein communication with the affected device(s) via a mesh network 270B tocourier communications to the MAD 210. When a connection is establishedat 272, MAD 210 obtain a payload of data, messages, and the like at 274.As part of obtaining the payload, system 200 may send a park signal P toacknowledge that the payload has been uploaded to the MAD. System 200may also use MAD 210 to perform various functions, generally indicatedat 275 including but not limited to transmitting an emergency modesignal; providing a survey/query to device(s); activating a GPS radiowithin one or more device; and transmitting the MAD schedule. Asdiscussed above, the park signal P may be used to transmit the signalsfrom MAD to carry out these functions. Alternatively, distinct signalsmay be provided.

With a payload on board, system 200 may signal MAD 210 to have it moveinto communication with a receiving site that is connected to a networkat 276. As before, communication may be established by moving the MAD toa location where communication can be established or MAD may beconnected to a device via mesh or other courier connection to thenetwork. Once MAD 210 drops the payload at 277, the messages/data may berouted to the recipient device 222 at 278. Data may also be communicatedto the community for review as generally indicated at 280. Community 230may use AI module and or machine learning module to analyze dataobtained from the at least one device in the offline community and/orother sources including but not limited to internal and external datasources, civic authorities and location information at 282. The analysis282 may include generating a representation of the at least onedevice(s), the event, the impact of the event on the network, possiblecollateral effects or combinations thereof at 283. This representationor other information from the community may be communicated to an outputdevice for further review or display at 284.

As discussed above, system 200 may implement the MOP via at least one ofa virtual network function, virtual machine or other network device.FIG. 3 illustrates a functional block diagram depicting one example of anetwork device, generally indicated at 300. Network device 300 maycomprise a processor 302 and a memory 304 coupled to processor 302.Memory 304 may contain executable instructions that, when executed byprocessor 302, cause processor 302 to effectuate operations associatedwith translating parallel protocols between end points in families asdescribed above. As evident from the description herein, network device300 is not to be construed as software per se.

In addition to processor 302 and memory 304, network device 300 mayinclude an input/output system 306. Processor 302, memory 304, andinput/output system 306 may be coupled together to allow communicationsbetween them. Each portion of network device 300 may comprise circuitryfor performing functions associated with each respective portion. Thus,each portion may comprise hardware, or a combination of hardware andsoftware. Accordingly, each portion of network device 300 is not to beconstrued as software per se. Input/output system 306 may be capable ofreceiving or providing information from or to a communications device orother network entities configured for telecommunications. For exampleinput/output system 306 may include a wireless communications (e.g.,3G/4G/GPS) card. Input/output system 306 may be capable of receiving orsending video information, audio information, control information, imageinformation, data, or any combination thereof. Input/output system 306may be capable of transferring information with network device 300. Invarious configurations, input/output system 306 may receive or provideinformation via any appropriate means, such as, for example, opticalmeans (e.g., infrared), electromagnetic means (e.g., RF, Wi-Fi,Bluetooth®, ZigBee®), acoustic means (e.g., speaker, microphone,ultrasonic receiver, ultrasonic transmitter), electrical means, or acombination thereof. In an example configuration, input/output system306 may comprise a Wi-Fi finder, a two-way GPS chipset or equivalent, orthe like, or a combination thereof. Bluetooth, infrared, NFC, and Zigbeeare generally considered short range (e.g., few centimeters to 20meters). WiFi is considered medium range (e.g., approximately 100meters).

Input/output system 306 of network device 300 also may contain acommunication connection 308 that allows network device 300 tocommunicate with other devices, network entities, or the like.Communication connection 308 may comprise communication media.Communication media typically embody computer-readable instructions,data structures, program modules or other data in a modulated datasignal such as a carrier wave or other transport mechanism and includesany information delivery media. By way of example, and not limitation,communication media may include wired media such as a wired network ordirect-wired connection, or wireless media such as acoustic, RF,infrared, or other wireless media. The term computer-readable media asused herein includes both storage media and communication media.Input/output system 306 also may include an input device 310 such askeyboard, mouse, pen, voice input device, or touch input device.Input/output system 306 may also include an output device 312, such as adisplay, speakers, or a printer.

Processor 302 may be capable of performing functions associated withtelecommunications, such as functions for processing broadcast messages,as described herein. For example, processor 302 may be capable of, inconjunction with any other portion of network device 300, determining atype of broadcast message and acting according to the broadcast messagetype or content, as described herein.

Memory 304 of network device 300 may comprise a storage medium having aconcrete, tangible, physical structure. As is known, a signal does nothave a concrete, tangible, physical structure. Memory 304, as well asany computer-readable storage medium described herein, is not to beconstrued as a signal. Memory 304, as well as any computer-readablestorage medium described herein, is not to be construed as a transientsignal. Memory 304, as well as any computer-readable storage mediumdescribed herein, is not to be construed as a propagating signal. Memory304, as well as any computer-readable storage medium described herein,is to be construed as an article of manufacture.

Memory 304 may store any information utilized in conjunction withtelecommunications. Depending upon the exact configuration or type ofprocessor, memory 304 may include a volatile storage 314 (such as sometypes of RAM), a nonvolatile storage 316 (such as ROM, flash memory), ora combination thereof. Memory 304 may include additional storage (e.g.,a removable storage 318 or a non-removable storage 320) including, forexample, tape, flash memory, smart cards, CD-ROM, DVD, or other opticalstorage, magnetic cassettes, magnetic tape, magnetic disk storage orother magnetic storage devices, USB-compatible memory, or any othermedium that can be used to store information and that can be accessed bynetwork device 300. Memory 304 may comprise executable instructionsthat, when executed by processor 302, cause processor 302 to effectuateoperations of the MOP including but not limited to discovery of devices220 affected by an event E, instantiating a community 230 including suchdevices, and aggregating data and signals from those devices in thecommunity 230.

System 200 may reside within any network. The following are examplenetworks on which system 200 may reside. For purposes of centrality,system 200 may reside within a core network shown in the variousexamples below. However, it will be understood that system 200 mayreside on any network edge router or network device providing the samefunction in connection with customer VRFs including but not limited totelecommunications networks, internet, and other networks described morecompletely below.

FIG. 4 illustrates a functional block diagram depicting one example ofan LTE-EPS network architecture 400 that may be at least partiallyimplemented as an SDN. Network architecture 400 disclosed herein isreferred to as a modified LTE-EPS architecture 400 to distinguish itfrom a traditional LTE-EPS architecture.

An example modified LTE-EPS architecture 400 is based at least in parton standards developed by the 3rd Generation Partnership Project (3GPP),with information available at www.3gpp.org. LTE-EPS network architecture400 may include an access network 402, a core network 404, e.g., an EPCor Common BackBone (CBB) and one or more external networks 406,sometimes referred to as PDN or peer entities. Different externalnetworks 406 can be distinguished from each other by a respectivenetwork identifier, e.g., a label according to DNS naming conventionsdescribing an access point to the PDN. Such labels can be referred to asAccess Point Names (APN). External networks 406 can include one or moretrusted and non-trusted external networks such as an internet protocol(IP) network 408, an IP multimedia subsystem (IMS) network 410, andother networks 412, such as a service network, a corporate network, orthe like. In an aspect, access network 402, core network 404, orexternal network 405 may include or communicate with network 100.

Access network 402 can include an LTE network architecture sometimesreferred to as Evolved Universal mobile Telecommunication systemTerrestrial Radio Access (E UTRA) and evolved UMTS Terrestrial RadioAccess Network (E-UTRAN). Broadly, access network 402 can include one ormore communication devices, commonly referred to as UE 414, and one ormore wireless access nodes, or base stations 416 a, 416 b. Duringnetwork operations, at least one base station 416 communicates directlywith UE 414. Base station 416 can be an evolved Node B (e-NodeB), withwhich UE 414 communicates over the air and wirelessly. UEs 414 caninclude, without limitation, wireless devices, e.g., satellitecommunication systems, portable digital assistants (PDAs), laptopcomputers, tablet devices and other mobile devices (e.g., cellulartelephones, smart appliances, and so on). UEs 414 can connect to eNBs416 when UE 414 is within range according to a corresponding wirelesscommunication technology.

UE 414 generally runs one or more applications that engage in a transferof packets between UE 414 and one or more external networks 406. Suchpacket transfers can include one of downlink packet transfers fromexternal network 406 to UE 414, uplink packet transfers from UE 414 toexternal network 406 or combinations of uplink and downlink packettransfers. Applications can include, without limitation, web browsing,VoIP, streaming media and the like. Each application can pose differentQuality of Service (QoS) requirements on a respective packet transfer.Different packet transfers can be served by different bearers withincore network 404, e.g., according to parameters, such as the QoS.

Core network 404 uses a concept of bearers, e.g., EPS bearers, to routepackets, e.g., IP traffic, between a particular gateway in core network404 and UE 414. A bearer refers generally to an IP packet flow with adefined QoS between the particular gateway and UE 414. Access network402, e.g., E UTRAN, and core network 404 together set up and releasebearers as required by the various applications. Bearers can beclassified in at least two different categories: (i) minimum guaranteedbit rate bearers, e.g., for applications, such as VoIP; and (ii)non-guaranteed bit rate bearers that do not require guarantee bit rate,e.g., for applications, such as web browsing.

In one embodiment, the core network 404 includes various networkentities, such as MME 418, SGW 420, Home Subscriber Server (HSS) 422,Policy and Charging Rules Function (PCRF) 424 and PGW 426. In oneembodiment, MME 418 comprises a control node performing a controlsignaling between various equipment and devices in access network 402and core network 404. The protocols running between UE 414 and corenetwork 404 are generally known as Non-Access Stratum (NAS) protocols.

For illustration purposes only, the terms MME 418, SGW 420, HSS 422 andPGW 426, and so on, can be server devices, but may be referred to in thesubject disclosure without the word “server.” It is also understood thatany form of such servers can operate in a device, system, component, orother form of centralized or distributed hardware and software. It isfurther noted that these terms and other terms such as bearer pathsand/or interfaces are terms that can include features, methodologies,and/or fields that may be described in whole or in part by standardsbodies such as the 3GPP. It is further noted that some or allembodiments of the subject disclosure may in whole or in part modify,supplement, or otherwise supersede final or proposed standards publishedand promulgated by 3GPP.

According to traditional implementations of LTE-EPS architectures, SGW420 routes and forwards all user data packets. SGW 420 also acts as amobility anchor for user plane operation during handovers between basestations, e.g., during a handover from first eNB 416 a to second eNB 416b as may be the result of UE 414 moving from one area of coverage, e.g.,cell, to another. SGW 420 can also terminate a downlink data path, e.g.,from external network 406 to UE 414 in an idle state, and trigger apaging operation when downlink data arrives for UE 414. SGW 420 can alsobe configured to manage and store a context for UE 414, e.g., includingone or more of parameters of the IP bearer service and network internalrouting information. In addition, SGW 420 can perform administrativefunctions, e.g., in a visited network, such as collecting informationfor charging (e.g., the volume of data sent to or received from theuser), and/or replicate user traffic, e.g., to support a lawfulinterception. SGW 420 also serves as the mobility anchor forinterworking with other 3GPP technologies such as universal mobiletelecommunication system (UMTS).

At any given time, UE 414 is generally in one of three different states:detached, idle, or active. The detached state is typically a transitorystate in which UE 414 is powered on but is engaged in a process ofsearching and registering with network 402. In the active state, UE 414is registered with access network 402 and has established a wirelessconnection, e.g., radio resource control (RRC) connection, with eNB 416.Whether UE 414 is in an active state can depend on the state of a packetdata session, and whether there is an active packet data session. In theidle state, UE 414 is generally in a power conservation state in whichUE 414 typically does not communicate packets. When UE 414 is idle, SGW420 can terminate a downlink data path, e.g., from one peer entity 406,and triggers paging of UE 414 when data arrives for UE 414. If UE 414responds to the page, SGW 420 can forward the IP packet to eNB 416 a.

HSS 422 can manage subscription-related information for a user of UE414. For example, tHSS 422 can store information such as authorizationof the user, security requirements for the user, quality of service(QoS) requirements for the user, etc. HSS 422 can also hold informationabout external networks 406 to which the user can connect, e.g., in theform of an APN of external networks 406. For example, MME 418 cancommunicate with HSS 422 to determine if UE 414 is authorized toestablish a call, e.g., a voice over IP (VoIP) call before the call isestablished.

PCRF 424 can perform QoS management functions and policy control. PCRF424 is responsible for policy control decision-making, as well as forcontrolling the flow-based charging functionalities in a policy controlenforcement function (PCEF), which resides in PGW 426. PCRF 424 providesthe QoS authorization, e.g., QoS class identifier and bit rates thatdecide how a certain data flow will be treated in the PCEF and ensuresthat this is in accordance with the user's subscription profile.

PGW 426 can provide connectivity between the UE 414 and one or more ofthe external networks 406. In illustrative network architecture 400, PGW426 can be responsible for IP address allocation for UE 414, as well asone or more of QoS enforcement and flow-based charging, e.g., accordingto rules from the PCRF 424. PGW 426 is also typically responsible forfiltering downlink user IP packets into the different QoS-based bearers.In at least some embodiments, such filtering can be performed based ontraffic flow templates. PGW 426 can also perform QoS enforcement, e.g.,for guaranteed bit rate bearers. PGW 426 also serves as a mobilityanchor for interworking with non-3GPP technologies such as CDMA2000.

Within access network 402 and core network 404 there may be variousbearer paths/interfaces, e.g., represented by solid lines 428 and 430.Some of the bearer paths can be referred to by a specific label. Forexample, solid line 428 can be considered an S1-U bearer and solid line432 can be considered an S5/S8 bearer according to LTE-EPS architecturestandards. Without limitation, reference to various interfaces, such asS1, X2, S5, S8, S11 refer to EPS interfaces. In some instances, suchinterface designations are combined with a suffix, e.g., a “U” or a “C”to signify whether the interface relates to a “User plane” or a “Controlplane.” In addition, the core network 404 can include various signalingbearer paths/interfaces, e.g., control plane paths/interfacesrepresented by dashed lines 430, 434, 436, and 438. Some of thesignaling bearer paths may be referred to by a specific label. Forexample, dashed line 430 can be considered as an S1-MME signalingbearer, dashed line 434 can be considered as an S11 signaling bearer anddashed line 436 can be considered as an S6a signaling bearer, e.g.,according to LTE-EPS architecture standards. The above bearer paths andsignaling bearer paths are only illustrated as examples and it should benoted that additional bearer paths and signaling bearer paths may existthat are not illustrated.

Also shown is a novel user plane path/interface, referred to as theS1-U+ interface 466. In the illustrative example, the S1-U+ user planeinterface extends between the eNB 416 a and PGW 426. Notably, S1-U+path/interface does not include SGW 420, a node that is otherwiseinstrumental in configuring and/or managing packet forwarding betweeneNB 416 a and one or more external networks 406 by way of PGW 426. Asdisclosed herein, the S1-U+ path/interface facilitates autonomouslearning of peer transport layer addresses by one or more of the networknodes to facilitate a self-configuring of the packet forwarding path. Inparticular, such self-configuring can be accomplished during handoversin most scenarios so as to reduce any extra signaling load on the S/PGWs420, 426 due to excessive handover events.

In some embodiments, PGW 426 is coupled to storage device 440, shown inphantom. Storage device 440 can be integral to one of the network nodes,such as PGW 426, for example, in the form of internal memory and/or diskdrive. It is understood that storage device 440 can include registerssuitable for storing address values. Alternatively or in addition,storage device 440 can be separate from PGW 426, for example, as anexternal hard drive, a flash drive, and/or network storage.

Storage device 440 selectively stores one or more values relevant to theforwarding of packet data. For example, storage device 440 can storeidentities and/or addresses of network entities, such as any of networknodes 418, 420, 422, 424, and 426, eNBs 416 and/or UE 414. In theillustrative example, storage device 440 includes a first storagelocation 442 and a second storage location 444. First storage location442 can be dedicated to storing a Currently Used Downlink address value442. Likewise, second storage location 444 can be dedicated to storing aDefault Downlink Forwarding address value 444. PGW 426 can read and/orwrite values into either of storage locations 442, 444, for example,managing Currently Used Downlink Forwarding address value 442 andDefault Downlink Forwarding address value 444 as disclosed herein.

In some embodiments, the Default Downlink Forwarding address for eachEPS bearer is the SGW S5-U address for each EPS Bearer. The CurrentlyUsed Downlink Forwarding address” for each EPS bearer in PGW 426 can beset every time when PGW 426 receives an uplink packet, e.g., a GTP-Uuplink packet, with a new source address for a corresponding EPS bearer.When UE 414 is in an idle state, the “Current Used Downlink Forwardingaddress” field for each EPS bearer of UE 414 can be set to a “null” orother suitable value.

In some embodiments, the Default Downlink Forwarding address is onlyupdated when PGW 426 receives a new SGW S5-U address in a predeterminedmessage or messages. For example, the Default Downlink Forwardingaddress is only updated when PGW 426 receives one of a Create SessionRequest, Modify Bearer Request and Create Bearer Response messages fromSGW 420.

As values 442, 444 can be maintained and otherwise manipulated on a perbearer basis, it is understood that the storage locations can take theform of tables, spreadsheets, lists, and/or other data structuresgenerally well understood and suitable for maintaining and/or otherwisemanipulate forwarding addresses on a per bearer basis.

It should be noted that access network 402 and core network 404 areillustrated in a simplified block diagram in FIG. 4. In other words,either or both of access network 402 and the core network 404 caninclude additional network elements that are not shown, such as variousrouters, switches and controllers. In addition, although FIG. 4illustrates only a single one of each of the various network elements,it should be noted that access network 402 and core network 404 caninclude any number of the various network elements. For example, corenetwork 404 can include a pool (i.e., more than one) of MMEs 418, SGWs420 or PGWs 426.

In the illustrative example, data traversing a network path between UE414, eNB 416 a, SGW 420, PGW 426 and external network 406 may beconsidered to constitute data transferred according to an end-to-end IPservice. However, for the present disclosure, to properly performestablishment management in LTE-EPS network architecture 400, the corenetwork, data bearer portion of the end-to-end IP service is analyzed.

An establishment may be defined herein as a connection set up requestbetween any two elements within LTE-EPS network architecture 400. Theconnection set up request may be for user data or for signaling. Afailed establishment may be defined as a connection set up request thatwas unsuccessful. A successful establishment may be defined as aconnection set up request that was successful.

In one embodiment, a data bearer portion comprises a first portion(e.g., a data radio bearer 446) between UE 414 and eNB 416 a, a secondportion (e.g., an S1 data bearer 428) between eNB 416 a and SGW 420, anda third portion (e.g., an S5/S8 bearer 432) between SGW 420 and PGW 426.Various signaling bearer portions are also illustrated in FIG. 4. Forexample, a first signaling portion (e.g., a signaling radio bearer 448)between UE 414 and eNB 416 a, and a second signaling portion (e.g., S1signaling bearer 430) between eNB 416 a and MME 418.

In at least some embodiments, the data bearer can include tunneling,e.g., IP tunneling, by which data packets can be forwarded in anencapsulated manner, between tunnel endpoints. Tunnels, or tunnelconnections can be identified in one or more nodes of network 100, e.g.,by one or more of tunnel endpoint identifiers, an IP address and a userdatagram protocol port number. Within a particular tunnel connection,payloads, e.g., packet data, which may or may not include protocolrelated information, are forwarded between tunnel endpoints.

An example of first tunnel solution 450 includes a first tunnel 452 abetween two tunnel endpoints 454 a and 456 a, and a second tunnel 452 bbetween two tunnel endpoints 454 b and 456 b. In the illustrativeexample, first tunnel 452 a is established between eNB 416 a and SGW420. Accordingly, first tunnel 452 a includes a first tunnel endpoint454 a corresponding to an S1-U address of eNB 416 a (referred to hereinas the eNB S1-U address), and second tunnel endpoint 456 a correspondingto an S1-U address of SGW 420 (referred to herein as the SGW S1-Uaddress). Likewise, second tunnel 452 b includes first tunnel endpoint454 b corresponding to an S5-U address of SGW 420 (referred to herein asthe SGW S5-U address), and second tunnel endpoint 456 b corresponding toan S5-U address of PGW 426 (referred to herein as the PGW S5-U address).

In at least some embodiments, first tunnel solution 450 is referred toas a two tunnel solution, e.g., according to the GPRS Tunneling ProtocolUser Plane (GTPv1-U based), as described in 3GPP specification TS29.281, incorporated herein in its entirety. It is understood that oneor more tunnels are permitted between each set of tunnel end points. Forexample, each subscriber can have one or more tunnels, e.g., one foreach PDP context that they have active, as well as possibly havingseparate tunnels for specific connections with different quality ofservice requirements, and so on.

An example of second tunnel solution 458 includes a single or directtunnel 460 between tunnel endpoints 462 and 464. In the illustrativeexample, direct tunnel 460 is established between eNB 416 a and PGW 426,without subjecting packet transfers to processing related to SGW 420.Accordingly, direct tunnel 460 includes first tunnel endpoint 462corresponding to the eNB S1-U address, and second tunnel endpoint 464corresponding to the PGW S5-U address. Packet data received at eitherend can be encapsulated into a payload and directed to the correspondingaddress of the other end of the tunnel. Such direct tunneling avoidsprocessing, e.g., by SGW 420 that would otherwise relay packets betweenthe same two endpoints, e.g., according to a protocol, such as the GTP-Uprotocol.

In some scenarios, direct tunneling solution 458 can forward user planedata packets between eNB 416 a and PGW 426, by way of SGW 420. That is,SGW 420 can serve a relay function, by relaying packets between twotunnel endpoints 416 a, 426. In other scenarios, direct tunnelingsolution 458 can forward user data packets between eNB 416 a and PGW426, by way of the S1 U+ interface, thereby bypassing SGW 420.

Generally, UE 414 can have one or more bearers at any one time. Thenumber and types of bearers can depend on applications, defaultrequirements, and so on. It is understood that the techniques disclosedherein, including the configuration, management and use of varioustunnel solutions 450, 458, can be applied to the bearers on anindividual bases. That is, if user data packets of one bearer, say abearer associated with a VoIP service of UE 414, then the forwarding ofall packets of that bearer are handled in a similar manner. Continuingwith this example, the same UE 414 can have another bearer associatedwith it through the same eNB 416 a. This other bearer, for example, canbe associated with a relatively low rate data session forwarding userdata packets through core network 404 simultaneously with the firstbearer. Likewise, the user data packets of the other bearer are alsohandled in a similar manner, without necessarily following a forwardingpath or solution of the first bearer. Thus, one of the bearers may beforwarded through direct tunnel 458; whereas, another one of the bearersmay be forwarded through a two-tunnel solution 450.

FIG. 5 depicts an exemplary diagrammatic representation of a machine inthe form of a computer system 500 within which a set of instructions,when executed, may cause the machine to perform any one or more of themethods described above. One or more instances of the machine canoperate, for example, as processor 302, UE 414, eNB 416, MME 418, SGW420, HSS 422, PCRF 424, PGW 426 and other devices of FIGS. 1, 2, and 4.In some embodiments, the machine may be connected (e.g., using a network502) to other machines. In a networked deployment, the machine mayoperate in the capacity of a server or a client user machine in aserver-client user network environment, or as a peer machine in apeer-to-peer (or distributed) network environment.

The machine may comprise a server computer, a client user computer, apersonal computer (PC), a tablet, a smart phone, a laptop computer, adesktop computer, a control system, a network router, switch or bridge,or any machine capable of executing a set of instructions (sequential orotherwise) that specify actions to be taken by that machine. It will beunderstood that a communication device of the subject disclosureincludes broadly any electronic device that provides voice, video ordata communication. Further, while a single machine is illustrated, theterm “machine” shall also be taken to include any collection of machinesthat individually or jointly execute a set (or multiple sets) ofinstructions to perform any one or more of the methods discussed herein.

Computer system 500 may include a processor (or controller) 504 (e.g., acentral processing unit (CPU)), a graphics processing unit (GPU, orboth), a main memory 506 and a static memory 508, which communicate witheach other via a bus 510. The computer system 500 may further include adisplay unit 512 (e.g., a liquid crystal display (LCD), a flat panel, ora solid state display). Computer system 500 may include an input device514 (e.g., a keyboard), a cursor control device 516 (e.g., a mouse), adisk drive unit 518, a signal generation device 520 (e.g., a speaker orremote control) and a network interface device 522. In distributedenvironments, the embodiments described in the subject disclosure can beadapted to utilize multiple display units 512 controlled by two or morecomputer systems 500. In this configuration, presentations described bythe subject disclosure may in part be shown in a first of display units512, while the remaining portion is presented in a second of displayunits 512.

The disk drive unit 518 may include a tangible computer-readable storagemedium 524 on which is stored one or more sets of instructions (e.g.,software 526) embodying any one or more of the methods or functionsdescribed herein, including those methods illustrated above.Instructions 526 may also reside, completely or at least partially,within main memory 506, static memory 508, or within processor 504during execution thereof by the computer system 500. Main memory 506 andprocessor 504 also may constitute tangible computer-readable storagemedia.

As shown in FIG. 6, telecommunication system 600 may include wirelesstransmit/receive units (WTRUs) 602, a RAN 604, a core network 606, apublic switched telephone network (PSTN) 608, the Internet 610, or othernetworks 612, though it will be appreciated that the disclosed examplescontemplate any number of WTRUs, base stations, networks, or networkelements. Each WTRU 602 may be any type of device configured to operateor communicate in a wireless environment. For example, a WTRU maycomprise drone 102, a mobile device, network device 300, or the like, orany combination thereof. By way of example, WTRUs 602 may be configuredto transmit or receive wireless signals and may include a UE, a mobilestation, a mobile device, a fixed or mobile subscriber unit, a pager, acellular telephone, a PDA, a smartphone, a laptop, a netbook, a personalcomputer, a wireless sensor, consumer electronics, or the like. WTRUs602 may be configured to transmit or receive wireless signals over anair interface 614.

Telecommunication system 600 may also include one or more base stations616. Each of base stations 616 may be any type of device configured towirelessly interface with at least one of the WTRUs 602 to facilitateaccess to one or more communication networks, such as core network 606,PTSN 608, Internet 610, or other networks 612. By way of example, basestations 616 may be a base transceiver station (BTS), a Node-B, an eNodeB, a Home Node B, a Home eNode B, a site controller, an access point(AP), a wireless router, or the like. While base stations 616 are eachdepicted as a single element, it will be appreciated that base stations616 may include any number of interconnected base stations or networkelements.

RAN 604 may include one or more base stations 616, along with othernetwork elements (not shown), such as a base station controller (BSC), aradio network controller (RNC), or relay nodes. One or more basestations 616 may be configured to transmit or receive wireless signalswithin a particular geographic region, which may be referred to as acell (not shown). The cell may further be divided into cell sectors. Forexample, the cell associated with base station 616 may be divided intothree sectors such that base station 616 may include three transceivers:one for each sector of the cell. In another example, base station 616may employ multiple-input multiple-output (MIMO) technology and,therefore, may utilize multiple transceivers for each sector of thecell.

Base stations 616 may communicate with one or more of WTRUs 602 over airinterface 614, which may be any suitable wireless communication link(e.g., RF, microwave, infrared (IR), ultraviolet (UV), or visiblelight). Air interface 614 may be established using any suitable radioaccess technology (RAT).

More specifically, as noted above, telecommunication system 600 may be amultiple access system and may employ one or more channel accessschemes, such as CDMA, TDMA, FDMA, OFDMA, SC-FDMA, or the like. Forexample, base station 616 in RAN 604 and WTRUs 602 connected to RAN 604may implement a radio technology such as Universal MobileTelecommunications System (UMTS) Terrestrial Radio Access (UTRA) thatmay establish air interface 614 using wideband CDMA (WCDMA). WCDMA mayinclude communication protocols, such as High-Speed Packet Access (HSPA)or Evolved HSPA (HSPA+). HSPA may include High-Speed Downlink PacketAccess (HSDPA) or High-Speed Uplink Packet Access (HSUPA).

As another example base station 616 and WTRUs 602 that are connected toRAN 604 may implement a radio technology such as Evolved UMTSTerrestrial Radio Access (E-UTRA), which may establish air interface 614using LTE or LTE-Advanced (LTE-A).

Optionally base station 616 and WTRUs 602 connected to RAN 604 mayimplement radio technologies such as IEEE 602.16 (i.e., WorldwideInteroperability for Microwave Access (WiMAX)), CDMA2000, CDMA2000 1×,CDMA2000 EV-DO, Interim Standard 2000 (IS-2000), Interim Standard 95(IS-95), Interim Standard 856 (IS-856), GSM, Enhanced Data rates for GSMEvolution (EDGE), GSM EDGE (GERAN), or the like.

Base station 616 may be a wireless router, Home Node B, Home eNode B, oraccess point, for example, and may utilize any suitable RAT forfacilitating wireless connectivity in a localized area, such as a placeof business, a home, a vehicle, a campus, or the like. For example, basestation 616 and associated WTRUs 602 may implement a radio technologysuch as IEEE 602.11 to establish a wireless local area network (WLAN).As another example, base station 616 and associated WTRUs 602 mayimplement a radio technology such as IEEE 602.15 to establish a wirelesspersonal area network (WPAN). In yet another example, base station 616and associated WTRUs 602 may utilize a cellular-based RAT (e.g., WCDMA,CDMA2000, GSM, LTE, LTE-A, etc.) to establish a picocell or femtocell.As shown in FIG. 6, base station 616 may have a direct connection toInternet 610. Thus, base station 616 may not be required to accessInternet 610 via core network 606.

RAN 604 may be in communication with core network 606, which may be anytype of network configured to provide voice, data, applications, and/orvoice over internet protocol (VoIP) services to one or more WTRUs 602.For example, core network 606 may provide call control, billingservices, mobile location-based services, pre-paid calling, Internetconnectivity, video distribution or high-level security functions, suchas user authentication. Although not shown in FIG. 6, it will beappreciated that RAN 604 or core network 606 may be in direct orindirect communication with other RANs that employ the same RAT as RAN604 or a different RAT. For example, in addition to being connected toRAN 604, which may be utilizing an E-UTRA radio technology, core network606 may also be in communication with another RAN (not shown) employinga GSM radio technology.

Core network 606 may also serve as a gateway for WTRUs 602 to accessPSTN 608, Internet 610, or other networks 612. PSTN 608 may includecircuit-switched telephone networks that provide plain old telephoneservice (POTS). For LTE core networks, core network 606 may use IMS core614 to provide access to PSTN 608. Internet 610 may include a globalsystem of interconnected computer networks or devices that use commoncommunication protocols, such as the transmission control protocol(TCP), user datagram protocol (UDP), or IP in the TCP/IP internetprotocol suite. Other networks 612 may include wired or wirelesscommunications networks owned or operated by other service providers.For example, other networks 612 may include another core networkconnected to one or more RANs, which may employ the same RAT as RAN 604or a different RAT.

Some or all WTRUs 602 in telecommunication system 600 may includemulti-mode capabilities. That is, WTRUs 602 may include multipletransceivers for communicating with different wireless networks overdifferent wireless links. For example, one or more WTRUs 602 may beconfigured to communicate with base station 616, which may employ acellular-based radio technology, and with base station 616, which mayemploy an IEEE 802 radio technology.

FIG. 7 is an example system 700 including RAN 604 and core network 606.As noted above, RAN 604 may employ an E-UTRA radio technology tocommunicate with WTRUs 602 over air interface 614. RAN 604 may also bein communication with core network 606.

RAN 604 may include any number of eNode-Bs 702 while remainingconsistent with the disclosed technology. One or more eNode-Bs 702 mayinclude one or more transceivers for communicating with the WTRUs 602over air interface 614. Optionally, eNode-Bs 702 may implement MIMOtechnology. Thus, one of eNode-Bs 702, for example, may use multipleantennas to transmit wireless signals to, or receive wireless signalsfrom, one of WTRUs 602.

Each of eNode-Bs 702 may be associated with a particular cell and may beconfigured to handle radio resource management decisions, handoverdecisions, scheduling of users in the uplink or downlink, or the like.As shown in FIG. 7 eNode-Bs 702 may communicate with one another over anX2 interface.

Core network 606 shown in FIG. 7 may include a mobility managementgateway or entity (MME) 704, a serving gateway 706, or a packet datanetwork (PDN) gateway 708. While each of the foregoing elements aredepicted as part of core network 606, it will be appreciated that anyone of these elements may be owned or operated by an entity other thanthe core network operator.

MME 704 may be connected to each of eNode-Bs 702 in RAN 604 via an S1interface and may serve as a control node. For example, MME 704 may beresponsible for authenticating users of WTRUs 602, bearer activation ordeactivation, selecting a particular serving gateway during an initialattach of WTRUs 602, or the like. MME 704 may also provide a controlplane function for switching between RAN 604 and other RANs (not shown)that employ other radio technologies, such as GSM or WCDMA.

Serving gateway 706 may be connected to each of eNode-Bs 702 in RAN 604via the S1 interface. Serving gateway 706 may generally route or forwarduser data packets to or from the WTRUs 602. Serving gateway 706 may alsoperform other functions, such as anchoring user planes duringinter-eNode B handovers, triggering paging when downlink data isavailable for WTRUs 602, managing or storing contexts of WTRUs 602, orthe like.

Serving gateway 706 may also be connected to PDN gateway 708, which mayprovide WTRUs 602 with access to packet-switched networks, such asInternet 610, to facilitate communications between WTRUs 602 andIP-enabled devices.

Core network 606 may facilitate communications with other networks. Forexample, core network 606 may provide WTRUs 602 with access tocircuit-switched networks, such as PSTN 608, such as through IMS core614, to facilitate communications between WTRUs 602 and traditionalland-line communications devices. In addition, core network 606 mayprovide the WTRUs 602 with access to other networks 612, which mayinclude other wired or wireless networks that are owned or operated byother service providers.

FIG. 8 depicts an overall block diagram of an example packet-basedmobile cellular network environment, such as a GPRS network as describedherein. In the example packet-based mobile cellular network environmentshown in FIG. 8, there are a plurality of base station subsystems (BSS)800 (only one is shown), each of which comprises a base stationcontroller (BSC) 802 serving a plurality of BTSs, such as BTSs 804, 806,808. BTSs 804, 806, 808 are the access points where users ofpacket-based mobile devices become connected to the wireless network. Inexample fashion, the packet traffic originating from mobile devices istransported via an over-the-air interface to BTS 808, and from BTS 808to BSC 802. Base station subsystems, such as BSS 800, are a part ofinternal frame relay network 810 that can include a service GPRS supportnodes (SGSN), such as SGSN 812 or SGSN 814. Each SGSN 812, 814 isconnected to an internal packet network 816 through which SGSN 812, 814can route data packets to or from a plurality of gateway GPRS supportnodes (GGSN) 818, 820, 822. As illustrated, SGSN 814 and GGSNs 818, 820,822 are part of internal packet network 816. GGSNs 818, 820, 822 mainlyprovide an interface to external IP networks such as PLMN 824, corporateintranets/internets 826, or Fixed-End System (FES) or the publicInternet 828. As illustrated, subscriber corporate network 826 may beconnected to GGSN 820 via a firewall 830. PLMN 824 may be connected toGGSN 820 via a boarder gateway router (BGR) 832. A Remote AuthenticationDial-In User Service (RADIUS) server 834 may be used for callerauthentication when a user calls corporate network 826.

Generally, there may be a several cell sizes in a network, referred toas macro, micro, pico, femto or umbrella cells. The coverage area ofeach cell is different in different environments. Macro cells can beregarded as cells in which the base station antenna is installed in amast or a building above average roof top level. Micro cells are cellswhose antenna height is under average roof top level. Micro cells aretypically used in urban areas. Pico cells are small cells having adiameter of a few dozen meters. Pico cells are used mainly indoors.Femto cells have the same size as pico cells, but a smaller transportcapacity. Femto cells are used indoors, in residential or small businessenvironments. On the other hand, umbrella cells are used to covershadowed regions of smaller cells and fill in gaps in coverage betweenthose cells.

FIG. 9 illustrates an architecture of a typical GPRS network 900 asdescribed herein. The architecture depicted in FIG. 9 may be segmentedinto four groups: users 902, RAN 904, core network 906, and interconnectnetwork 908. Users 902 comprise a plurality of end users, who each mayuse one or more devices 910. Note that device 910 is referred to as amobile subscriber (MS) in the description of network shown in FIG. 9. Inan example, device 910 comprises a communications device (e.g., mobiledevice 102, mobile positioning center 116, network device 300, any ofdetected devices 500, second device 508, access device 604, accessdevice 606, access device 608, access device 610 or the like, or anycombination thereof). Radio access network 904 comprises a plurality ofBSSs such as BSS 912, which includes a BTS 914 and a BSC 916. Corenetwork 906 may include a host of various network elements. Asillustrated in FIG. 9, core network 906 may comprise MSC 918, servicecontrol point (SCP) 920, gateway MSC (GMSC) 922, SGSN 924, home locationregister (HLR) 926, authentication center (AuC) 928, domain name system(DNS) server 930, and GGSN 932. Interconnect network 908 may alsocomprise a host of various networks or other network elements. Asillustrated in FIG. 9, interconnect network 908 comprises a PSTN 934, anFES/Internet 936, a firewall 1038 (FIG. 10), or a corporate network 940.

An MSC can be connected to a large number of BSCs. At MSC 918, forinstance, depending on the type of traffic, the traffic may be separatedin that voice may be sent to PSTN 934 through GMSC 922, or data may besent to SGSN 924, which then sends the data traffic to GGSN 932 forfurther forwarding.

When MSC 918 receives call traffic, for example, from BSC 916, it sendsa query to a database hosted by SCP 920, which processes the request andissues a response to MSC 918 so that it may continue call processing asappropriate.

HLR 926 is a centralized database for users to register to the GPRSnetwork. HLR 926 stores static information about the subscribers such asthe International Mobile Subscriber Identity (IMSI), subscribedservices, or a key for authenticating the subscriber. HLR 926 alsostores dynamic subscriber information such as the current location ofthe MS. Associated with HLR 926 is AuC 928, which is a database thatcontains the algorithms for authenticating subscribers and includes theassociated keys for encryption to safeguard the user input forauthentication.

In the following, depending on context, “mobile subscriber” or “MS”sometimes refers to the end user and sometimes to the actual portabledevice, such as a mobile device, used by an end user of the mobilecellular service. When a mobile subscriber turns on his or her mobiledevice, the mobile device goes through an attach process by which themobile device attaches to an SGSN of the GPRS network. In FIG. 9, whenMS 910 initiates the attach process by turning on the networkcapabilities of the mobile device, an attach request is sent by MS 910to SGSN 924. The SGSN 924 queries another SGSN, to which MS 910 wasattached before, for the identity of MS 910. Upon receiving the identityof MS 910 from the other SGSN, SGSN 924 requests more information fromMS 910. This information is used to authenticate MS 910 together withthe information provided by HLR 926. Once verified, SGSN 924 sends alocation update to HLR 926 indicating the change of location to a newSGSN, in this case SGSN 924. HLR 926 notifies the old SGSN, to which MS910 was attached before, to cancel the location process for MS 910. HLR926 then notifies SGSN 924 that the location update has been performed.At this time, SGSN 924 sends an Attach Accept message to MS 910, whichin turn sends an Attach Complete message to SGSN 924.

Next, MS 910 establishes a user session with the destination network,corporate network 940, by going through a Packet Data Protocol (PDP)activation process. Briefly, in the process, MS 910 requests access tothe Access Point Name (APN), for example, UPS.com, and SGSN 924 receivesthe activation request from MS 910. SGSN 924 then initiates a DNS queryto learn which GGSN 932 has access to the UPS.com APN. The DNS query issent to a DNS server within core network 906, such as DNS server 930,which is provisioned to map to one or more GGSNs in core network 906.Based on the APN, the mapped GGSN 932 can access requested corporatenetwork 940. SGSN 924 then sends to GGSN 932 a Create PDP ContextRequest message that contains necessary information. GGSN 932 sends aCreate PDP Context Response message to SGSN 924, which then sends anActivate PDP Context Accept message to MS 910.

Once activated, data packets of the call made by MS 910 can then gothrough RAN 904, core network 906, and interconnect network 908, in aparticular FES/Internet 936 and firewall 1038, to reach corporatenetwork 940.

FIG. 10 illustrates a block diagram of an example PLMN architecture thatmay be replaced by a telecommunications system. In FIG. 10, solid linesmay represent user traffic signals, and dashed lines may representsupport signaling. MS 1002 is the physical equipment used by the PLMNsubscriber. For example, drone 102, network device 300, the like, or anycombination thereof may serve as MS 1002. MS 1002 may be one of, but notlimited to, a cellular telephone, a cellular telephone in combinationwith another electronic device or any other wireless mobilecommunication device.

MS 1002 may communicate wirelessly with BSS 1004. BSS 1004 contains BSC1006 and a BTS 1008. BSS 1004 may include a single BSC 1006/BTS 1008pair (base station) or a system of BSC/BTS pairs that are part of alarger network. BSS 1004 is responsible for communicating with MS 1002and may support one or more cells. BSS 1004 is responsible for handlingcellular traffic and signaling between MS 1002 and a core network 1010.Typically, BSS 1004 performs functions that include, but are not limitedto, digital conversion of speech channels, allocation of channels tomobile devices, paging, or transmission/reception of cellular signals.

Additionally, MS 1002 may communicate wirelessly with RNS 1012. RNS 1012contains a Radio Network Controller (RNC) 1014 and one or more Nodes B1016. RNS 1012 may support one or more cells. RNS 1012 may also includeone or more RNC 1014/Node B 1016 pairs or alternatively a single RNC1014 may manage multiple Nodes B 1016. RNS 1012 is responsible forcommunicating with MS 1002 in its geographically defined area. RNC 1014is responsible for controlling Nodes B 1016 that are connected to it andis a control element in a UMTS radio access network. RNC 1014 performsfunctions such as, but not limited to, load control, packet scheduling,handover control, security functions, or controlling MS 1002 access tocore network 1010.

An E-UTRA Network (E-UTRAN) 1018 is a RAN that provides wireless datacommunications for MS 1002 and UE 1024. E-UTRAN 1018 provides higherdata rates than traditional UMTS. It is part of the LTE upgrade formobile networks, and later releases meet the requirements of theInternational Mobile Telecommunications (IMT) Advanced and are commonlyknown as a 4G networks. E-UTRAN 1018 may include of series of logicalnetwork components such as E-UTRAN Node B (eNB) 1020 and E-UTRAN Node B(eNB) 1022. E-UTRAN 1018 may contain one or more eNBs. User equipment(UE) 1024 may be any mobile device capable of connecting to E-UTRAN 1018including, but not limited to, a personal computer, laptop, mobiledevice, wireless router, or other device capable of wirelessconnectivity to E-UTRAN 1018. The improved performance of the E-UTRAN1018 relative to a typical UMTS network allows for increased bandwidth,spectral efficiency, and functionality including, but not limited to,voice, high-speed applications, large data transfer or IPTV, while stillallowing for full mobility.

Typically MS 1002 may communicate with any or all of BSS 1004, RNS 1012,or E-UTRAN 1018. In a illustrative system, each of BSS 1004, RNS 1012,and E-UTRAN 1018 may provide MS 1002 with access to core network 1010.Core network 1010 may include of a series of devices that route data andcommunications between end users. Core network 1010 may provide networkservice functions to users in the circuit switched (CS) domain or thepacket switched (PS) domain. The CS domain refers to connections inwhich dedicated network resources are allocated at the time ofconnection establishment and then released when the connection isterminated. The PS domain refers to communications and data transfersthat make use of autonomous groupings of bits called packets. Eachpacket may be routed, manipulated, processed or handled independently ofall other packets in the PS domain and does not require dedicatednetwork resources.

The circuit-switched MGW function (CS-MGW) 1026 is part of core network1010, and interacts with VLR/MSC server 1028 and GMSC server 1030 inorder to facilitate core network 1010 resource control in the CS domain.Functions of CS-MGW 1026 include, but are not limited to, mediaconversion, bearer control, payload processing or other mobile networkprocessing such as handover or anchoring. CS-MGW 1026 may receiveconnections to MS 1002 through BSS 1004 or RNS 1012.

SGSN 1032 stores subscriber data regarding MS 1002 in order tofacilitate network functionality. SGSN 1032 may store subscriptioninformation such as, but not limited to, the IMSI, temporary identities,or PDP addresses. SGSN 1032 may also store location information such as,but not limited to, GGSN address for each GGSN 1034 where an active PDPexists. GGSN 1034 may implement a location register function to storesubscriber data it receives from SGSN 1032 such as subscription orlocation information.

Serving gateway (S-GW) 1036 is an interface which provides connectivitybetween E-UTRAN 1018 and core network 1010. Functions of S-GW 1036include, but are not limited to, packet routing, packet forwarding,transport level packet processing, or user plane mobility anchoring forinter-network mobility. PCRF 1038 uses information gathered from P-GW1036, as well as other sources, to make applicable policy and chargingdecisions related to data flows, network resources or other networkadministration functions. PDN gateway (PDN-GW) 1040 may provideuser-to-services connectivity functionality including, but not limitedto, GPRS/EPC network anchoring, bearer session anchoring and control, orIP address allocation for PS domain connections.

HSS 1042 is a database for user information and stores subscription dataregarding MS 1002 or UE 1024 for handling calls or data sessions.Networks may contain one HSS 1042 or more if additional resources arerequired. Example data stored by HSS 1042 include, but is not limitedto, user identification, numbering or addressing information, securityinformation, or location information. HSS 1042 may also provide call orsession establishment procedures in both the PS and CS domains.

VLR/MSC Server 1028 provides user location functionality. When MS 1002enters a new network location, it begins a registration procedure. A MSCserver for that location transfers the location information to the VLRfor the area. A VLR and MSC server may be located in the same computingenvironment, as is shown by VLR/MSC server 1028, or alternatively may belocated in separate computing environments. A VLR may contain, but isnot limited to, user information such as the IMSI, the Temporary MobileStation Identity (TMSI), the Local Mobile Station Identity (LMSI), thelast known location of the mobile station, or the SGSN where the mobilestation was previously registered. The MSC server may containinformation such as, but not limited to, procedures for MS 1002registration or procedures for handover of MS 1002 to a differentsection of core network 1010. GMSC server 1030 may serve as a connectionto alternate GMSC servers for other MSs in larger networks.

EIR 1044 is a logical element which may store the IMEI for MS 1002. Userequipment may be classified as either “white listed” or “black listed”depending on its status in the network. If MS 1002 is stolen and put touse by an unauthorized user, it may be registered as “black listed” inEIR 1044, preventing its use on the network. A MME 1046 is a controlnode which may track MS 1002 or UE 1024 if the devices are idle.Additional functionality may include the ability of MME 1046 to contactidle MS 1002 or UE 1024 if retransmission of a previous session isrequired.

As described herein, a telecommunications system wherein management andcontrol utilizing a software designed network (SDN) and a simple IP arebased, at least in part, on user equipment, may provide a wirelessmanagement and control framework that enables common wireless managementand control, such as mobility management, radio resource management,QoS, load balancing, etc., across many wireless technologies, e.g. LTE,Wi-Fi, and future 5G access technologies; decoupling the mobilitycontrol from data planes to let them evolve and scale independently;reducing network state maintained in the network based on user equipmenttypes to reduce network cost and allow massive scale; shortening cycletime and improving network upgradability; flexibility in creatingend-to-end services based on types of user equipment and applications,thus improve customer experience; or improving user equipment powerefficiency and battery life—especially for simple M2M devices—throughenhanced wireless management.

While examples of a telecommunications system in which emergency alertscan be processed and managed have been described in connection withvarious computing devices/processors, the underlying concepts may beapplied to any computing device, processor, or system capable offacilitating a telecommunications system. The various techniquesdescribed herein may be implemented in connection with hardware orsoftware or, where appropriate, with a combination of both. Thus, themethods and devices may take the form of program code (i.e.,instructions) embodied in concrete, tangible, storage media having aconcrete, tangible, physical structure. Examples of tangible storagemedia include floppy diskettes, CD-ROMs, DVDs, hard drives, or any othertangible machine-readable storage medium (computer-readable storagemedium). Thus, a computer-readable storage medium is not a signal. Acomputer-readable storage medium is not a transient signal. Further, acomputer-readable storage medium is not a propagating signal. Acomputer-readable storage medium as described herein is an article ofmanufacture. When the program code is loaded into and executed by amachine, such as a computer, the machine becomes an device fortelecommunications. In the case of program code execution onprogrammable computers, the computing device will generally include aprocessor, a storage medium readable by the processor (includingvolatile or nonvolatile memory or storage elements), at least one inputdevice, and at least one output device. The program(s) can beimplemented in assembly or machine language, if desired. The languagecan be a compiled or interpreted language, and may be combined withhardware implementations.

The methods and devices associated with a telecommunications system asdescribed herein also may be practiced via communications embodied inthe form of program code that is transmitted over some transmissionmedium, such as over electrical wiring or cabling, through fiber optics,or via any other form of transmission, wherein, when the program code isreceived and loaded into and executed by a machine, such as an EPROM, agate array, a programmable logic device (PLD), a client computer, or thelike, the machine becomes an device for implementing telecommunicationsas described herein. When implemented on a general-purpose processor,the program code combines with the processor to provide a unique devicethat operates to invoke the functionality of a telecommunicationssystem.

EXAMPLES Example 1

A data parking in an offline community system comprising: a discoverymodule configured to identify at least one device that has gone offlinedue to an event; a community, the community including at least one datasource, the data source including the identity of the at least onedevice; and a mobile aggregation device movable between a first positionwhere the mobile aggregation device is in communication with a networkto a second position to establish communication with the at least onedevice; wherein the mobile aggregation device is configured to aggregatedata from the at least one device and store it until returning to thefirst position.

Example 2

The system of example 1, wherein the data stored in the mobileaggregation device is deployed to the network when the mobileaggregation device returns to the first position.

Example 3

The system of example 1, wherein the mobile aggregation device isconfigured to transmit a parked signal to the at least one device whenthe mobile aggregation device is in the second position.

Example 4

The system of example 3, wherein the parked signal includes at least oneof an emergency mode signal, acknowledgement signal, a survey signal, aquery signal, and a mobile aggregation device schedule signal.

Example 5

The system of example 4, wherein the mobile aggregation device isconfigured to await a response from the at least one device aftersending at least one of the survey signal and the query signal.

Example 6

The system of example 4, wherein upon returning to the first position,mobile aggregation device communicates a device status signal based on aresponse or lack of a response from the at least one device to theparked signal.

Example 7

The system of example 1, wherein the community further comprises anartificial intelligence instantiated as a virtual network function ornetwork device, wherein the community communicates with the mobileaggregation device to receive data from the at least one device, andwherein the artificial intelligence is configured to assess the eventbased on the data obtained by the mobile aggregation device.

Example 8

The system of example 1, wherein the mobile aggregation devicecommunicates data from the at least one device to the community, andwherein the community includes a display, wherein the community isconfigured to provide an output representing the impact of the event.

Example 9

The system of example 1, wherein the mobile aggregation device isconfigured to transmit a signal to the at least one device when firstreaching the second position placing the device in an emergency mode.

Example 10

The system of example 1, wherein the mobile aggregation device isconfigured to transmit a signal to the at least one device activatingthe GPS radio in the at least one device.

Example 11

The system of example 1, wherein the community is configured to identifya role associated with the at least one device, and assign a priority tothe at least one device based on the role, wherein the priority includesat least one of a communication priority, a time order priority, aconnectivity priority and a data priority.

Example 12

The system of example 11, wherein the communication priority identifiesat least one priority device in the at least one device that is offlineto the mobile aggregation device, wherein when the mobile aggregationdevice moves to the second position, data from the at least one prioritydevice is uploaded before data from the at least one device that has notbeen identified as having priority.

Example 13

The system of example 1, wherein the community is configured to predictflow or target for the at least one device that is offline based on anetwork condition.

Example 14

A network device comprising: a processor, an input/output device coupledto the processor, and a memory coupled with the processor, the memorycomprising executable instructions that when executed by the processorcause the processor to effectuate operations comprising discovering anevent where at least one device is offline; instantiating an emergencymode causing the at least one device to permit data or messageaggregation; instantiating a community including the identity of the atleast one device; establishing communication between the at least onedevice and a mobile aggregation device; and when the mobile aggregationdevice is in communication with the at least one device, aggregating apayload of the message or data from the at least one device.

Example 15

The network device of example 14, wherein the operations furthercomprise moving the mobile aggregation device to establish communicationwith a receiving site in communication with a network, and deploying thepayload to the network via the receiving site.

Example 16

The network device of example 14, wherein the step of establishingincludes moving the mobile aggregation device into communication with anaggregation site, wherein the aggregation site is in communication withthe at least one device.

Example 17

The network device of example 16, the step of instantiating emergencymode includes boosting a signal at the aggregation site, when the mobileaggregation is in communication with the aggregation site.

Example 18

The network device of example 14, wherein after the step ofestablishing, the operations include sending a parked signal to the atleast one device.

Example 19

The network device of example 18, wherein the parked signal includes atleast one of an emergency mode display signal, an acknowledgementsignal, a survey signal, a query signal, and a mobile aggregation deviceschedule signal.

Example 20

The network device of example 14, wherein the operations furthercomprise gathering data within the community relating to the at leastone device and generating a representation of the event from the datawithin the community and communicating the representation via theoutput.

1. A data parking in an offline community system comprising: a discoverymodule configured to identify at least one device that has gone offlinedue to an event; a community, the community including at least one datasource, the data source including the identity of the at least onedevice; and a mobile aggregation device movable between a first positionwhere the mobile aggregation device is in communication with a networkto a second position to establish communication with the at least onedevice; wherein the mobile aggregation device is configured to aggregatedata from the at least one device and store it until returning to thefirst position.
 2. The system of claim 1, wherein the data stored in themobile aggregation device is deployed to the network when the mobileaggregation device returns to the first position.
 3. The system of claim1, wherein the mobile aggregation device is configured to transmit aparked signal to the at least one device when the mobile aggregationdevice is in the second position.
 4. The system of claim 3, wherein theparked signal includes at least one of an emergency mode signal,acknowledgement signal, a survey signal, a query signal, and a mobileaggregation device schedule signal.
 5. The system of claim 4, whereinthe mobile aggregation device is configured to await a response from theat least one device after sending at least one of the survey signal andthe query signal.
 6. The system of claim 4, wherein upon returning tothe first position, mobile aggregation device communicates a devicestatus signal based on a response or lack of a response from the atleast one device to the parked signal.
 7. The system of claim 1, whereinthe community further comprises an artificial intelligence instantiatedas a virtual network function or network device, wherein the communitycommunicates with the mobile aggregation device to receive data from theat least one device, and wherein the artificial intelligence isconfigured to assess the event based on the data obtained by the mobileaggregation device.
 8. The system of claim 1, wherein the mobileaggregation device communicates data from the at least one device to thecommunity, and wherein the community includes a display, wherein thecommunity is configured to provide an output representing the impact ofthe event.
 9. The system of claim 1, wherein the mobile aggregationdevice is configured to transmit a signal to the at least one devicewhen first reaching the second position placing the device in anemergency mode.
 10. The system of claim 1, wherein the mobileaggregation device is configured to transmit a signal to the at leastone device activating the GPS radio in the at least one device.
 11. Thesystem of claim 1, wherein the community is configured to identify arole associated with the at least one device, and assign a priority tothe at least one device based on the role, wherein the priority includesat least one of a communication priority, a time order priority, aconnectivity priority and a data priority.
 12. The system of claim 11,wherein the communication priority identifies at least one prioritydevice in the at least one device that is offline to the mobileaggregation device, wherein when the mobile aggregation device moves tothe second position, data from the at least one priority device isuploaded before data from the at least one device that has not beenidentified as having priority.
 13. The system of claim 1, wherein thecommunity is configured to predict flow or target for the at least onedevice that is offline based on a network condition.
 14. A networkdevice comprising: a processor, an input/output device coupled to theprocessor, and a memory coupled with the processor, the memorycomprising executable instructions that when executed by the processorcause the processor to effectuate operations comprising: discovering anevent where at least one device is offline; instantiating an emergencymode causing the at least one device to permit data or messageaggregation; instantiating a community including the identity of the atleast one device; establishing communication between the at least onedevice and a mobile aggregation device; and when the mobile aggregationdevice is in communication with the at least one device, aggregating apayload of the message or data from the at least one device.
 15. Thenetwork device of claim 14, wherein the operations further comprisemoving the mobile aggregation device to establish communication with areceiving site in communication with a network, and deploying thepayload to the network via the receiving site.
 16. The network device ofclaim 14, wherein the step of establishing includes moving the mobileaggregation device into communication with an aggregation site, whereinthe aggregation site is in communication with the at least one device.17. The network device of claim 16, the step of instantiating emergencymode includes boosting a signal at the aggregation site, when the mobileaggregation is in communication with the aggregation site.
 18. Thenetwork device of claim 14, wherein after the step of establishing, theoperations include sending a parked signal to the at least one device.19. The network device of claim 18, wherein the parked signal includesat least one of an emergency mode display signal, an acknowledgementsignal, a survey signal, a query signal, and a mobile aggregation deviceschedule signal.
 20. The network device of claim 14, wherein theoperations further comprise gathering data within the community relatingto the at least one device and generating a representation of the eventfrom the data within the community and communicating the representationvia the output.